feat(pipeline): Add inference and lineage step types - #6224

Adds four pipeline step classes -- EndpointConfigStep, EndpointStep,
InferenceComponentStep and LineageStep -- along with their StepTypeEnum
values and package exports.

Each step takes step_args captured under a PipelineSession, following
the convention used by TrainingStep and ModelStep:

- Session.endpoint_from_production_variants, Session.create_endpoint
  and Session.create_inference_component route their service calls
  through _intercept_create_request. Under a plain Session this is a
  pass-through; under a PipelineSession the request is captured and no
  service call is made.
- LineageStep records one lineage entity per step, with step_args from
  Action.create(), Artifact.create(), Context.create() or
  Association.create(). Record._invoke_api captures those four calls
  under a PipelineSession. An association can reference an entity
  created by another step via Steps.<name>.ActionArns['<entity>'].
- Each step validates the provenance of its step_args with
  validate_step_args_input, rejecting a wrong producer or a raw dict.

Note for chaining: the resource created by an EndpointConfig step
carries an execution-unique name suffix, so a downstream step must
reference it as config_step.properties.EndpointConfigName rather than
the requested name.

Tested with 29 unit tests plus two integration tests that exercise all
four step types end to end against the service.
---
X-AI-Prompt: Add the new inference and lineage pipeline step types to
the public SDK, using step_args captured via PipelineSession per review
feedback, and verify them with integration tests
X-AI-Tool: kiro-cli